\chapter{Conclusion}
	In this report we have covered the aspects of a board game. We have accomplished this by looking at Tic-Tac-Toe, Checkers, Ludo and Connect 4. We took a look at their what rules, components and flow the different games used and after we had established the general elements of board game, we moved on to find what our language should look like to be easy to use for programmers with both little experience and much experience. We created a code structure and defined the general characteristics of the language. We implemented with focus on our design criteria to insure it was meeting our expectations.
	We compared the differences between a compiler and interpreter and decided to go for the interpreter.
	After agreeing on the interpreter we started on the implementation.
	We developed the language and managed to implement an interpreter. We have implemented two games (Tic-Tac-Toe and Connect 4) to show that the interpreter works. After testing the two games we concluded we reaced our expectation and that it was possible to implement multiple board games in CLUBs. But there are still features that do not work properly in CLUBs. One of the things we still are missing to implement are for loops, arrays and switch statements.
	We also took a look at some possible changes to the language in the future, e.g. another way to describe the representation of boards using a editor.

	If we look back at our goals for this project, we have accomplished most of them.
	\begin{itemize}
	\item Learn about programming language and make our own programming language: \\ We have accomplished this by looking at a lot of different programing languages to create CLUBs.
	\item Construct a grammar and syntax for our language: \\ We have created our own EBNF and ATG. A descripion of the important aspect of the syntax, like block structure etc.
	\item Our programming language should be easy to read, write and learn: \\ 
	The actual goal of making it easier to prototype a board game on the computer, than making a typical prototype on paper, is not at all accomplished. We believe this goal could be better accomplished by implementing the features described in the Future Work section. However, in relation to prototyping board games in common programming languages, CLUBs provides an easier alternative. 
	\item Learn about compilers and interpreters: \\ Accomplished in the section concerning this.
	\item Make a working interpreter or compiler: \\ Accomplished, but not all features are implemented.
	\item Implement acception of user defined rules: \\ Accomplished in form of \textit{action}'s.
	\item Valuable for testing the board game: \\ It would most likly be faster to make a small paper prototype by hand.
	\item Get errors if the programmer makes a mistake in his or her code: \\ Some errors are posted if the programmer makes mistakes, but more advanced and specific error messages could have helped to reach this goal.
	\end{itemize}
	
	
	